From: Florian Müllner <fmuellner@gnome.org>
Date: Mon, 9 Nov 2020 19:24:34 +0000 (+0100)
Subject: ci: Enforce non-legacy style for new code
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~616^2^2~756
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=25ca8826ed71629a5e5028b2e20a2a3f7fd3c2ec;p=gnome-shell.git

ci: Enforce non-legacy style for new code

We have been transitioning to the new coding style for a while now,
and there has been reasonable progress. So hopefully it is not too
intrusive at this point to enforce non-legacy style for all lines
that are changed in a merge request. If it turns out to be still too
annoying, we can always reconsider and turn off the additional job.

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1497
---

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 195bb8a6d..581ef2ba0 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -10,6 +10,7 @@ variables:
     BUNDLE: "extensions-git.flatpak"
     JS_LOG: "js-report.txt"
     LINT_LOG: "eslint-report.xml"
+    LINT_MR_LOG: "eslint-mr-report.xml"
 
 .only_default: &only_default
     only:
@@ -51,6 +52,21 @@ eslint:
             junit: ${LINT_LOG}
         when: always
 
+eslint_mr:
+    image: registry.gitlab.gnome.org/gnome/gnome-shell/extension-ci:v2
+    stage: review
+    script:
+        - export NODE_PATH=$(npm root -g)
+        - ./.gitlab-ci/run-eslint --output-file ${LINT_MR_LOG} --format junit
+            --remote ${CI_MERGE_REQUEST_PROJECT_URL}.git
+            --branch ${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}
+    only:
+        - merge_requests
+    artifacts:
+        reports:
+            junit: ${LINT_MR_LOG}
+        when: always
+
 potfile_check:
     image: registry.gitlab.gnome.org/gnome/gnome-shell/extension-ci:v2
     stage: review